Systems and methods for integrated, secure point-of-sale transactions having an adjustable base station

ABSTRACT

A system for processing transactions, having at least one mobile device having a housing having a processor, and a Wi-Fi Communication module disposed therein; a base station having a base station housing, wherein the base station housing houses an embedded system including a processor; and a Wi-Fi communication module configured to communicate with the Wi-Fi communication module of the at least one mobile device; a support stand configured to support the at least one mobile device, wherein the support stand comprises at least one arm having an adjustable position and configured to move to adjust the size of the support stand based on a size of the at least one mobile device; and at least one peripheral device connected to the base station.

BACKGROUND

1. Field

The embodiments described herein relate to point-of-sale (POS)transactions and more specifically to systems and methods that enableintegrated and secure POS transactions using low cost tablet devices.

2. Description of the Related Art

A conventional POS system comprises a large cash register. EarlyElectronic Cash Registers (ECRs) were controlled by proprietary softwareand had limited functionality. Eventually these ECR's were able tointerface with a backend system that provided accounting, reporting andother functionality. But these earlier systems in addition to beingphysically bulky were also typically proprietary systems in that therewere no uniform standards across the industry. Often, these systems wereserver-client systems that were costly to own and operate.

More recently, the availability of local processing power, local datastorage, networking, and graphical user interface made it possible todevelop flexible and highly functional POS systems. Cost of such systemshas also declined, as all the components can now be purchasedoff-the-shelf. A conventional retail POS system now typically includes acomputer, monitor, cash drawer, receipt printer, customer display and abarcode scanner, and the majority of retail POS systems also include adebit/credit card reader. It can also include a weight scale, integratedcredit card processing system, a signature capture device and a customerpin pad device. At the core of the modern POS system is some type of CPUthat runs the POS system. The other components are then peripherals thatcan be interfaced with the CPU as needed.

More and more POS monitors use touch-screen technology for ease of useand a computer is built in to the monitor chassis for what is referredto as an all-in-one unit. All-in-one POS units liberate counter spacefor the retailer. The POS system software can typically handle myriadcustomer based functions such as sales, returns, exchanges, layaways,gift cards, gift registries, customer loyalty programs, BOGOF (buy oneget one free), quantity discounts and much more. POS software can alsoallow for functions such as pre-planned promotional sales, manufacturercoupon validation, foreign currency handling and multiple payment types.

In the retail environment, the POS unit handles the sales to theconsumer but it is only one part of the entire POS system used in aretail business. “Back-office” computers typically handle otherfunctions of the POS system such as inventory control, purchasing,receiving and transferring of products to and from other locations.Other typical functions of a POS system are to store sales informationfor reporting purposes, sales trends and cost/price/profit analysis.Customer information may be stored for receivables management, marketingpurposes and specific buying analysis. Many retail POS systems includean accounting interface that “feeds” sales and cost of goods informationto independent accounting applications.

Moreover, recently new applications have been introduced that enable POStransactions to be conducted using mobile phones and tablets. Newentrants include Square, Intuit's GoPayments, and NCR Inc.'s Silverplatform, ezyMART POS, ShopKeep POS, and GoPago. This is an importantdevelopment, because in the United States alone, there are over 5million small merchants who do not handle a large amount of transaction.As a result, they are very price sensitive toward the POS system and thepayment system.

A major problem with these newer, mobile device centric systems is thatthey lack the necessary security. The more conventional systemsdescribed above suffer from higher cost, and limited flexibility.Another issue with these conventional systems the material flow, e.g.,the process around reading the bar code on an item, and the paymentprocess are two separate processes run by different applications.

SUMMARY

The embodiments described herein are related to system and methods for atablet or mobile based POS system that provides the necessary securityand integrated material and payment processing.

One aspect provides a system for processing transactions, comprising: atleast one mobile device comprising a housing having a processor, and aWi-Fi Communication module disposed therein; and a base stationcomprising a base station housing, wherein the base station housinghouses an embedded system comprising: a processor, and a Wi-Ficommunication module configured to communicate with the Wi-Ficommunication module of the at least one mobile device, a support standconfigured to support the at least one mobile device, wherein thesupport stand comprises at least one arm having an adjustable positionand configured to move to adjust the size of the support stand based ona size of the at least one mobile device; and at least one peripheraldevice connected to the base station.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of the present invention, both as to its structure andoperation, may be gleaned in part by study of the accompanying drawings,in which like reference numerals refer to like parts, and in which:

FIG. 1 illustrates a first perspective view of base station according toa first embodiment of the present application.

FIG. 2 illustrates a second perspective view of the base station.

FIG. 3 illustrates a front view of the base station with a mobiledevice;

FIG. 4 illustrates a back view of the base station and mobile device;

FIG. 5A-5E illustrates several enlarged views of various portions of thebase station;

FIG. 6 illustrates a block diagram of the electronic hardware of thebase station; and

FIG. 7 illustrates a block diagram illustrating an example wired orwireless system that may be used as or in conjunction embodiments of thepresent application.

FIG. 8 illustrates a flow chart of a payment process using the basestation and mobile device.

FIG. 9 illustrates a flow chart of an inventory process using the basestation and the mobile device.

FIG. 10 provides a block diagram showing a first embodiment of thesoftware level architecture, and interaction between, an embodiment ofthe base station and one or more mobile devices.

FIG. 11A provides a block diagram showing a second embodiment of thesoftware level architecture, and interaction between, an embodiment ofthe base station and one or more mobile devices.

FIG. 11B provides a block diagram showing a third embodiment of thesoftware level architecture, and interaction between, an embodiment ofthe base station and one or more mobile devices.

FIGS. 12A-12D provide perspective views of a case for the tablet havinga card reader incorporated directly into the case.

DETAILED DESCRIPTION

The embodiments described herein have several aspects that will bedescribed. These aspects include the hardware designs, e.g., thephysical stand, base, interconnections, etc.; the electronic hardwaredesign; the software design; and the communication processes. Each ofthese aspects is described in detail below.

Hardware

The embodiments described herein include a base stations and a mobiledevice such as a tablet device. FIGS. 1 and 2 illustrate an example basestation 102 configured in accordance with on example embodiment. As canbe seen, base station 102 can comprise or act as a base to hold themobile device or tablet. Thus, base station 102 can include a baseportion 104 and a support portion 106 for holding the mobile or tabletdevice. The base station 102 can also provide charging function for themobile or tablet device, as well as connection to an external wirelessrouter. In certain embodiments, the base station can include a router.The base station 102 can also include a processor and memory asdescribed in more detail below.

Using a mobile device or tablet allows the device to be removed fromsupport portion 106 so that it can be moved throughout a store or retaillocation. The tablet can provide the user interface needed to processtransactions, the base station's processor can be configured to thenprocess the transaction. Other peripherals can then be added in amodular fashion to base station 102. For example, a scanner(s), printer,register, card reader, etc., can be added to or interfaced with basestation 102. Thus, base station 102 can include various Input-Output(I/O) ports, such as a RJ12 24V cash register port, RS232 ports with5V/12V support for printer and VFD display, one USB port for a bar codescanner and three other USB expansion ports, e.g., one on the front andthe other in the rear, a 10/100M Ethernet interface, a stereo audioport, or some combination thereof. It will be understood that these arejust examples.

In certain embodiments, the support portion 106 can swivel asillustrated in FIGS. 3 and 4. As can be seen in FIGS. 3 and 4, whichprovide front and back views, the base 108 of support 106 can swivel inthese implementations.

FIG. 5A is a diagram with another support portion 106 that can adjust tofit different sized tablets or mobile devices via adjustable arms 110and 112, which can slide in and out. Also, support portion 106 can beconfigured such that it can be elongated or collapsed in order to movetop arms 110 up and down. FIGS. 5B and 5C illustrate an alternativeembodiment of base station 102 that use the support portion 106 of FIG.5A. As can be seen, base station 102 sits on base portion 113. The I/Oports can be seen on the back of base station 102 in FIG. 5C. Also, ascanner or card reader 107 can be built into base station 102 asillustrated in both FIGS. 5B and 5C. The adjustable portion 105 ofsupport portion 106 can be seen in FIG. 5C.

FIG. 5D illustrates the base station 102 and adjustable support portion106 of FIGS. 5A-C integrated with a cash register 120 and a printer 122.

In the embodiment of FIG. 5E, support portion 106 includes arms 112 thatcan slide outward or inward as needed.

While not illustrated, certain embodiments can include a casing for thetablet through which the tablet can interface with base station 102. Thecase can either be a water resistant design or a basic version. Thecasing can allow for charging through a standard port on the basestation allowing the same base station to support multiple tablet modelsdespite the various connector designs and locations. The charging portwill also allow for the base station 102 to sense that the tablet isphysically present for cash transactions preventing the cash drawer frominadvertently deploying when the sales associate is not present.Further, a cash drawer may be opened accidentally where the cashier maycomplete the transaction on the floor but he or she is not present atthe cash drawer. Therefore, by adding a physical detection of the tabletbeing on the stand by adding the contact pin or RFID reader, this errorcan be prevented. The cashier has to physically go back to the cashdrawer and install the stand before he or she can open the cash drawer.In some embodiments, the application can support multiple tablets on onestation by assigning each tablet a unique identification number throughthe use of an RFID tag adhered to the back of each tablet. A readerinstalled on the stand connected to the base station will allow the basestation to authenticate that the tablet performing the transaction isphysically located at the base station.

FIGS. 12A-12D provide perspective views of a case 1400 for a tablet 1404having a card reader 1410 incorporated directly into the case 1400. Thecase 1400 includes a front frame 1402, a rear inner case 1406, and arear outer case 1414. The front frame 1402 and the rear inner case 1406surround the tablet 1404 from the front and back sides respectively. Thefront frame 1402 and the rear inner case 1406 are configured to engageeach other and create a seal around the tablet 1404 within the case1400. The rear inner case 1406 may also include a hinged stand 1412 thatcan be opened to support tablet in an upright orientation. The rearinner case 1406 also may have a card reader receiving portion 1416 tohold the card reader 1410. In the embodiment shown in FIG. 12A, the cardreader receiving portion 1416 may include a slot or groove configured toreceive the card reader 1410. Further, a locking member 1408 may beprovided to hold the card reader 1410 in the card reader receivingportion 1416. The rear outer case 1414 is configured to attach to therear of the rear inner case 1406 after the card reader 1410 has beeninserted in to the card reader receiving portion 1416.

Electronic Hardware

FIG. 6 is a diagram illustrating the electronic hardware components of abase station 102 configured in accordance with one embodiment. As can beseen, from an electronic hardware perspective, base station 102 caninclude a processor or CPU as well as main program memory, DDR RAM,FLASH, etc., in hardware block 202. This block 202 can also include anEMV processing and encryption capability as described in more detailbelow.

Block 202 can be interfaced with a Wi-Fi module 204, a non-volatilememory such as an Electrically Erasable Programmable Memory (EEPROM)206, a POS function block 208, and a transaction function block 210. Aunique identifier (VID/PID) and other information can be stored in thenon-volatile memory 206 inside base station. The tablet can use thisdata for authentication between the tablet and the base station 102.

POS block 208 can include a secured storage 212. All confidentialcustomer data, business data and transaction data can bepassword-protected and DES/AES encrypted and stored in this drive. Onlywith the correct password and matched base station can the stored databe accessed. POS block 208 can also include various interface modulesincluding a RJ12 port 214, a RS232 transceiver 216 can port 218, a USBto Ethernet controller 220, transformer 222, and RJ45 port 224, and aplurality of USB ports such as ports 226 and 228.

Transaction function block 210 can comprise magnetic stripe card reader,a secured magnetic strip card reader and a smartcard reader module 230as well as interfaces for a contactless reader 232 and PINpad (PersonalIdentification Number Pad) 234. The architecture of a secured magneticstripe reader includes a magnetic stripe reader head, a flexible PCB anda 8-bit Micro CPU. The magnetic stripe reader head has three tracks andhas six pins out from the reader head. A three layer flexible PCB issoldered to the six pins on the reader head. An epoxy is used to pot theconnection between the reader head and the flexible PCB to provide itwith security. The flexible PCB has three layers and the top and thebottom layers are designed with electronic fence to prevent any thieffrom tapping the magnetic stripe traces. The micro CPU is soldered on asmall PCB and is potted with epoxy and protected with a PCB basedelectronic fence to prevent anyone from probing the CPU. This gives thebase station a physical security protection for the magnetic stripereader. The CPU will encrypt the magnetic stripe data in the potted areaand will send the encrypted data to the base station to complete thetransaction.

Base station 102 can also include a tablet interface block 236 throughwhich power can be supplied to the tablet. In certain embodiments, anaudio port 238 can also be interfaced with tablet interface block 236.Base station 102 can also include a power input 240 and a powerconverter 242 configured to convert the, e.g., 24V input from powerinput 240 into various voltage signals for use by the modules and blocksthat comprise base station 102.

The hardware components can be used by multiple applications, ormultiple tablets. For example, the WTA application, described in detailbelow, can require hardware device management functionality to handleresource allocation arrangement. The WTA can compensate for thecapability of the associated tablet, e.g., an iPad without the use ofJailbreak to control multiple peripherals in the base station 102without requiring the user to disconnect and connect to the variouscomponents. Initial setup of base station 102 can be performed throughconnecting the base station 102 to the network via an Ethernet port 224.Once configured the base station 102 can operate wirelessly or viaEthernet connection.

It will be understood that the diagram of FIG. 6 is a high level diagramand that other or fewer components can be included. Thus theillustration of FIG. 6 should not be seen as limiting in any way. Itwill also be understood that any of the components illustrated can beimplemented using multiple devices and our distributed resources.

More generically, FIG. 7 is a block diagram illustrating an examplewired or wireless system 550 that may be used in connection with variousembodiments described herein. For example the system 550 may be used asor in conjunction with one or more of the mechanisms or processesdescribed above, and may represent components of processors 202, usersystem(s), and/or other devices described herein. The system 550 can bea server or any conventional personal computer, or any otherprocessor-enabled device that is capable of wired or wireless datacommunication. Other computer systems and/or architectures may be alsoused, as will be clear to those skilled in the art.

The system 550 preferably includes one or more processors, such asprocessor 560. Additional processors may be provided, such as anauxiliary processor to manage input/output, an auxiliary processor toperform floating point mathematical operations, a special-purposemicroprocessor having an architecture suitable for fast execution ofsignal processing algorithms (e.g., digital signal processor), a slaveprocessor subordinate to the main processing system (e.g., back-endprocessor), an additional microprocessor or controller for dual ormultiple processor systems, or a coprocessor. Such auxiliary processorsmay be discrete processors or may be integrated with the processor 560.Examples of processors which may be used with system 550 include,without limitation, the Pentium® processor, Core i7® processor, andXeon® processor, all of which are available from Intel Corporation ofSanta Clara, Calif.

The processor 560 is preferably connected to a communication bus 555.The communication bus 555 may include a data channel for facilitatinginformation transfer between storage and other peripheral components ofthe system 550. The communication bus 555 further may provide a set ofsignals used for communication with the processor 560, including a databus, address bus, and control bus (not shown). The communication bus 555may comprise any standard or non-standard bus architecture such as, forexample, bus architectures compliant with industry standard architecture(ISA), extended industry standard architecture (EISA), Micro ChannelArchitecture (MCA), peripheral component interconnect (PCI) local bus,or standards promulgated by the Institute of Electrical and ElectronicsEngineers (IEEE) including IEEE 488 general-purpose interface bus(GPIB), IEEE 696/S-100, and the like.

System 550 preferably includes a main memory 565 and may also include asecondary memory 570. The main memory 565 provides storage ofinstructions and data for programs executing on the processor 560, suchas one or more of the functions and/or modules discussed above. Itshould be understood that programs stored in the memory and executed byprocessor 560 may be written and/or compiled according to any suitablelanguage, including without limitation C/C++, Java, JavaScript, Pearl,Visual Basic, .NET, and the like. The main memory 565 is typicallysemiconductor-based memory such as dynamic random access memory (DRAM)and/or static random access memory (SRAM). Other semiconductor-basedmemory types include, for example, synchronous dynamic random accessmemory (SDRAM), Rambus dynamic random access memory (RDRAM),ferroelectric random access memory (FRAM), and the like, including readonly memory (ROM).

The secondary memory 570 may optionally include an internal memory 575and/or a removable medium 580, for example a floppy disk drive, amagnetic tape drive, a compact disc (CD) drive, a digital versatile disc(DVD) drive, other optical drive, a flash memory drive, etc. Theremovable medium 580 is read from and/or written to in a well-knownmanner. Removable storage medium 580 may be, for example, a floppy disk,magnetic tape, CD, DVD, SD card, etc.

The removable storage medium 580 is a non-transitory computer-readablemedium having stored thereon computer executable code (i.e., software)and/or data. The computer software or data stored on the removablestorage medium 580 is read into the system 550 for execution by theprocessor 560.

In alternative embodiments, secondary memory 570 may include othersimilar means for allowing computer programs or other data orinstructions to be loaded into the system 550. Such means may include,for example, an external storage medium 595 and an interface 590.Examples of external storage medium 595 may include an external harddisk drive or an external optical drive, or and external magneto-opticaldrive.

Other examples of secondary memory 570 may include semiconductor-basedmemory such as programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), electrically erasable read-onlymemory (EEPROM), or flash memory (block oriented memory similar toEEPROM). Also included are any other removable storage media 580 andcommunication interface 590, which allow software and data to betransferred from an external medium 595 to the system 550.

System 550 may include a communication interface 590. The communicationinterface 590 allows software and data to be transferred between system550 and external devices (e.g. printers), networks, or informationsources. For example, computer software or executable code may betransferred to system 550 from a network server via communicationinterface 590. Examples of communication interface 590 include abuilt-in network adapter, network interface card (NIC), PersonalComputer Memory Card International Association (PCMCIA) network card,card bus network adapter, wireless network adapter, Universal Serial Bus(USB) network adapter, modem, a network interface card (NIC), a wirelessdata card, a communications port, an infrared interface, an IEEE 1394fire-wire, or any other device capable of interfacing system 550 with anetwork or another computing device.

Communication interface 590 preferably implements industry promulgatedprotocol standards, such as Ethernet IEEE 802 standards, Fiber Channel,digital subscriber line (DSL), asynchronous digital subscriber line(ADSL), frame relay, asynchronous transfer mode (ATM), integrateddigital services network (ISDN), personal communications services (PCS),transmission control protocol/Internet protocol (TCP/IP), serial lineInternet protocol/point to point protocol (SLIP/PPP), and so on, but mayalso implement customized or non-standard interface protocols as well.

Software and data transferred via communication interface 590 aregenerally in the form of electrical communication signals 605. Thesesignals 605 are preferably provided to communication interface 590 via acommunication channel 600. In one embodiment, the communication channel600 may be a wired or wireless network, or any variety of othercommunication links. Communication channel 600 carries signals 605 andcan be implemented using a variety of wired or wireless communicationmeans including wire or cable, fiber optics, conventional phone line,cellular phone link, wireless data communication link, radio frequency(“RF”) link, or infrared link, just to name a few.

Computer executable code (i.e., computer programs or software) is storedin the main memory 565 and/or the secondary memory 570. Computerprograms can also be received via communication interface 590 and storedin the main memory 565 and/or the secondary memory 570. Such computerprograms, when executed, enable the system 550 to perform the variousfunctions of the present invention as previously described.

In this description, the term “computer readable medium” is used torefer to any non-transitory computer readable storage media used toprovide computer executable code (e.g., software and computer programs)to the system 550. Examples of these media include main memory 565,secondary memory 570 (including internal memory 575, removable medium580, and external storage medium 595), and any peripheral devicecommunicatively coupled with communication interface 590 (including anetwork information server or other network device). Thesenon-transitory computer readable mediums are means for providingexecutable code, programming instructions, and software to the system550.

In an embodiment that is implemented using software, the software may bestored on a computer readable medium and loaded into the system 550 byway of removable medium 580, I/O interface 585, or communicationinterface 590. In such an embodiment, the software is loaded into thesystem 550 in the form of electrical communication signals 605. Thesoftware, when executed by the processor 560, preferably causes theprocessor 560 to perform the inventive features and functions previouslydescribed herein.

In an embodiment, I/O interface 585 provides an interface between one ormore components of system 550 and one or more input and/or outputdevices. Example input devices include, without limitation, keyboards,touch screens or other touch-sensitive devices, biometric sensingdevices, computer mice, trackballs, pen-based pointing devices, and thelike. Examples of output devices include, without limitation, cathoderay tubes (CRTs), plasma displays, light-emitting diode (LED) displays,liquid crystal displays (LCDs), printers, vacuum florescent displays(VFDs), surface-conduction electron-emitter displays (SEDs), fieldemission displays (FEDs), and the like.

The system 550 also includes optional wireless communication componentsthat facilitate wireless communication over a voice and over a datanetwork. The wireless communication components comprise an antennasystem 610, a radio system 615 and a baseband system 620. In the system550, radio frequency (RF) signals are transmitted and received over theair by the antenna system 610 under the management of the radio system615.

In one embodiment, the antenna system 610 may comprise one or moreantennae and one or more multiplexors (not shown) that perform aswitching function to provide the antenna system 610 with transmit andreceive signal paths. In the receive path, received RF signals can becoupled from a multiplexor to a low noise amplifier (not shown) thatamplifies the received RF signal and sends the amplified signal to theradio system 615.

In alternative embodiments, the radio system 615 may comprise one ormore radios that are configured to communicate over various frequencies.In one embodiment, the radio system 615 may combine a demodulator (notshown) and modulator (not shown) in one integrated circuit (IC). Thedemodulator and modulator can also be separate components. In theincoming path, the demodulator strips away the RF carrier signal leavinga baseband receive audio signal, which is sent from the radio system 615to the baseband system 620.

If the received signal contains audio information, then baseband system620 decodes the signal and converts it to an analog signal. Then thesignal is amplified and sent to a speaker. The baseband system 620 alsoreceives analog audio signals from a microphone. These analog audiosignals are converted to digital signals and encoded by the basebandsystem 620. The baseband system 620 also codes the digital signals fortransmission and generates a baseband transmit audio signal that isrouted to the modulator portion of the radio system 615. The modulatormixes the baseband transmit audio signal with an RF carrier signalgenerating an RF transmit signal that is routed to the antenna systemand may pass through a power amplifier (not shown). The power amplifieramplifies the RF transmit signal and routes it to the antenna system 610where the signal is switched to the antenna port for transmission.

The baseband system 620 is also communicatively coupled with theprocessor 560. The central processing unit 560 has access to datastorage areas 565 and 570. The central processing unit 560 is preferablyconfigured to execute instructions (i.e., computer programs or software)that can be stored in the memory 565 or the secondary memory 570.Computer programs can also be received from the baseband processor 610and stored in the data storage area 565 or in secondary memory 570, orexecuted upon receipt. Such computer programs, when executed, enable thesystem 550 to perform the various functions of the present invention aspreviously described. For example, data storage areas 565 may includevarious software modules (not shown).

Various embodiments may also be implemented primarily in hardware using,for example, components such as application specific integrated circuits(ASICs), or field programmable gate arrays (FPGAs). Implementation of ahardware state machine capable of performing the functions describedherein will also be apparent to those skilled in the relevant art.Various embodiments may also be implemented using a combination of bothhardware and software.

Furthermore, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and method stepsdescribed in connection with the above described figures and theembodiments disclosed herein can often be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled persons can implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the invention. In addition, the grouping of functions within amodule, block, circuit or step is for ease of description. Specificfunctions or steps can be moved from one module, block or circuit toanother without departing from the invention.

Moreover, the various illustrative logical blocks, modules, functions,and methods described in connection with the embodiments disclosedherein can be implemented or performed with a general purpose processor,a digital signal processor (DSP), an ASIC, FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor can be a microprocessor,but in the alternative, the processor can be any processor, controller,microcontroller, or state machine. A processor can also be implementedas a combination of computing devices, for example, a combination of aDSP and a microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

Additionally, the steps of a method or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module can reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of storage mediumincluding a network storage medium. An exemplary storage medium can becoupled to the processor such the processor can read information from,and write information to, the storage medium. In the alternative, thestorage medium can be integral to the processor. The processor and thestorage medium can also reside in an ASIC.

Communication Process Overview

Software running on the mobile device may allow the mobile device tointeract with the base station and perform both payment POS activitiesas well perform activities related to monitoring and maintaininginventory. FIG. 8 illustrates a process for performing a paymentoperation using the mobile device and base station according to anembodiment of the present application. FIG. 9 illustrates a process forperforming a POS operation using the mobile device and base stationaccording to an embodiment of the present application.

In the payment operation (i.e. a payment transaction) shown in FIG. 8,the system must first be initialized and the user (i.e. a salesrepresentative, for example) must login as shown by S801. In someembodiments, this involves authenticating by the base station of themobile device and authenticating by the mobile device the base stationin order to ensure that a secure transaction in a commercialenvironment. Thus, an embedded system within the base station maycommunicate with a mobile device using a Wi-Fi Transportation Authority(WTA). The WTA is made up of a pair of applications, one residing on themobile device, and one residing on the base station. In someembodiments, the WTA application residing on the mobile device may bereplaced with a thin-client application running on a host server andaccessed through a browser. Thus, in the case of a thin clientapplication, the WTA is made up of a pair of applications, one residingon the host server which is accessed through the browser on the mobiledevice, and one application residing on the base station.

Together the pair of applications facilitates communication between themobile device and the system embedded within the base station. Throughthe WTA, the mobile device and the base station authenticate each otherprior to any sales transactions being processed to ensure that onlyauthorized mobile devices working in conjunction with authorized basestations can execute sales transactions. Without the properauthenticated WTA application installed, a mobile device cannotcommunicate with the base station. Additionally, a unique identifier(VID/PID) may be stored by the system embedded in the base station andto complete authentication a user may be required to enter theidentifier through the mobile device.

Additionally, a separate POS application may be used to perform the POSoperations. In other words, a separate POS application running inparallel with the WTA application is used to perform the POStransactions. The POS application uses the WTA application tocommunicate with the base station and thus must be authenticated by theWTA application to communicate with the base station. Further, the datamay be transmitted between the WTAs may be further encrypted using Wi-FiWEP/WPA encryption.

Additionally, a Terminal Management System (TMS) download tool may beused to download authentication information so that a paymentapplication can be downloaded to the base station to perform the basestation side of POS transactions. The TMS also locks the paymentapplication to prevent unauthorized downloading of applications into thebase station.

Additionally, in some embodiments a pin pad may be used in combinationwith base station and mobile device to allow a customer to key inpersonal identification information for payment transactions. In suchembodiments, the pin pad is authenticated by the base station during theauthentication of S801 to ensure that only the approved pin pad can beused with the base station.

Once the system has self-authenticated and a user (i.e. salesrepresentative) has logged in, the system enters an idle state in S802.During the idle state, the system waits for the user to initiate apayment transaction. During S802, the system monitors how long thesystem has been in an idle state. If the system determines it has beenin an idle state for an amount of time that exceeds a threshold (i.e. 5minutes, 10 minutes, etc.), the system may automatically logout in S803so that login and authentication of S801 must be repeated to preventaccess by an unauthorized person.

In S804, the authorized user (i.e. sales representative) selects apayment transaction function using the POS application to begin apayment transaction. This may be done through any method of interfaceapparent to a person of ordinary skill in the art. For example, anauthorized user may touch a control button on a displayed userinterface.

In some embodiments, the user may be provided with an interface forentry of customer information (i.e. customer name, mailing address,email address, telephone, zip code, etc.) in S805 once the paymenttransaction has been selected. The user may enter the customerinformation using the displayed interface. In some embodiments, the usermay elect to bypass the customer information and proceed to paymentinformation entry in S806.

In S806, the authenticated user enters payment information using themobile device. In some embodiments, the user may enter paymentinformation by swiping a credit card through a card reader incommunication with the mobile device or the base station. Connectionbetween the mobile device or base station and the credit card reader canbe achieved through either wired or wireless communication.

After the credit card information has been entered, a customer can berequested to provide a pin number associated with card information inS807 using the authenticated pin pad device discussed above.

Once the pin number has been provided, payment transaction informationindicating the purchase value amount and the payment information isprovided to the authorized user (i.e. the sales representative) in S808so that any errors can be detected prior to transmission to thefinancial institution associated with the credit card. After the paymenttransaction information is provided to the authorized user, the userconfirms the accuracy of the information in S809.

Once the payment transaction has been confirmed, the payment module onthe base station connects to a gateway server through the base stationand sends a request for payment confirmation of the transaction in S810.Once the request for payment confirmation is sent in S810, the paymentmodule on the base station goes into an idle state awaiting a reply fromthe Gateway server in S811.

Once a reply or result is received from the gateway server in S811, thetransaction data, including the payment information and the confirmationresult returned by the gateway server, is stored in the secured storagedevice of the embedded system of the base station in S812. Additionally,once the result is returned by the gateway server, a merchant receiptmay be printed using a printer in communication with the base station(communication may be wired or wireless) in S813. Additionally, acustomer receipt may also be printed using the printer in S814.

Finally, the payment module on the base station may store the paymenttransaction information in batches with other payment transactions inS815. Once the payment transaction is successfully stored in batch, thesystem returns to the idle state of S802 awaiting another transaction tobe initiated. Again, if the system is idle for a period of timeexceeding a threshold, the system may automatically logout to preventunauthorized access.

FIG. 9 illustrates a process for performing an POS operation using themobile device and base station according to an embodiment of the presentapplication.

In the POS operation (i.e. a payment transaction) shown in FIG. 9, thesystem must first be initialized and the user (i.e. a salesrepresentative, for example) must login as shown by S901. In someembodiments, this involves authenticating by the base station of themobile device and authenticating by the mobile device the base stationin order to ensure that a secure transaction in a commercialenvironment. Thus, an embedded system within the base station cancommunicate with mobile device using a Wi-Fi Transportation Authority(WTA). The WTA is made up of a pair of applications, one residing on themobile device, and one residing on the base station or host for thethin-client application accessed through the browser.

Together the pair of applications facilitates communication between themobile device and the system embedded within the base station. Throughthe WTA, the mobile device and the base station authenticate each otherprior to any transactions being processed to ensure that only authorizedmobile devices working in conjunction with authorized base stations canexecute sales transactions. Without the proper authenticated WTAapplication installed or securely accessed to the host through abrowser, a mobile device cannot communicate with the base station.Additionally, a unique identifier (VID/PID) may be stored by the systemembedded in the base station and to complete authentication a user maybe required to enter the identifier through the mobile device.

Additionally, a separate POS application may be used to perform the POSoperations. In other words, a separate POS application running inparallel with the WTA application is used to perform the POStransactions. The POS application uses the WTA application tocommunicate with the base station and thus must be authenticated by theWTA application to communicate with the base station.

Additionally, a Terminal Management System (TMS) download tool may beused to download authentication information to the base station so thata payment application can be downloaded to perform the base station sideof POS transactions. The TMS also locks the payment application toprevent unauthorized downloading of applications into the base station.

Additionally, in some embodiments a pin pad may be used in combinationwith base station and mobile device to allow a customer to key inpersonal identification information for payment transactions. In suchembodiments, the pin pad is authenticated by both the mobile device andthe base station during the authentication of S901 to ensure that onlythe approved pin pad can be used with the base station.

Once the system has self-authenticated and a user (i.e. salesrepresentative) has logged in, the system enters an idle state in S902.During the idle state, the system waits for the user to initiate a POStransaction (i.e. access the inventory application). During S902, thesystem monitors how long the system has been in an idle state. If thesystem determines it has been in an idle state for an amount of timethat exceeds a threshold (i.e. 5 minutes, 10 minutes, etc.), the systemmay automatically logout in S903 so that login and authentication ofS901 must be repeated to prevent access by an unauthorized person.

Once the authorized user (i.e. sales representative) initiates aninventory transaction, the POS application is activated to access theinventory information through the POS application in S904. Thus, theinventory may be updated to reflect any items being purchased and thepricing information for purchased items may be retrieved from securedstorage located within the base station. Once the inventory is updatedand the pricing is retrieved, the POS data is re-saved to the securedstorage located within the base station in S905.

Once the POS data is accessed, retrieved, and updated to the securedstorage, the retrieved pricing information is transmitted to the paymentapplication in S906 and a payment process is performed according to theprocess discussed above with respect to FIG. 8. Once the paymenttransaction is completed, the payment data is saved to the securedstorage of the base station in S907.

Once the payment process has been completed in S906 and the payment datais saved to the secured storage of the base station in S907, a paymentreceipt may be printed for a customer records using a printer incommunication with the base station (i.e. a printer connected throughwired or wireless connection with the base station). Further, a salesreceipt for store records may also be printed using the printer in S909.Once the sales receipt is printed in S909, the system may return to anidle state in S902 and await subsequent transactions. Again, if thesystem is in an idle state for a period of time exceeding a threshold,the system may automatically log out in S903 to prevent unauthorizedaccess.

Thus, as indicated, the transaction information is stored in basestation 102. Moreover, the base station and whatever peripheral but inparticular the mobile device must co-authenticate each other before thedevice or peripheral will be granted access to the transactioninformation. The TMS ensures that only valid and authorized processingapplications are loaded onto the base station. All of this ensures thatthe data can be safely maintained on the base station, which in turnallows the base station to communicate with several devices and storethe aggregate transaction information. Moreover, if a device is stolen,it will not include the transaction information.

Software Architecture

FIG. 10 provides a block diagram showing the software levelarchitecture, and interaction between, an embodiment of the base station1000 and one or more mobile devices 1100, 1200, 1300. Though differentmobile devices (i.e. an Apple IPAD 1100, a Samsung Galaxy Tab 2 1200, aMicrosoft RT Surface 1300) may be used, a number of features can stillbe common to the mobile device used regardless of what type of mobiledevice is selected. Specifically, in mobile device 1100, 1200, 1300includes a POS application 1101, 1201, 1301 that is used to perform thePOS transactions, a Payment User interface application 1102, 1202, 1301and a WTA application 1103, 1203, 1303, which is configured to interfacewith the individual operating systems 1104, 1204, 1304 of the differentmobile devices 1100, 1200, 1300. Additionally, each of the differentmobile devices 1100, 1200, 1300 may also have a Wi-Fi driver 1105, 1205,1305 configured to allow each of the individual operating systems 1104,1204, 1304 to control a Wi-Fi device 1106, 1206, 1306 integrated intothe mobile devices 1100, 1200, 1300 to allow wireless communication withthe base station 1000.

As discussed above, the base station 1000 includes an embedded system(Best terminal (BT)) that is independent from the mobile device 1000,1200, 1300. The embedded system includes its own software that caninclude a payment application 1001, EMV L2 application 1002, and aterminal management system 1003 that each interface with a WTAapplication 1004. The WTA Application 1004 allows the paymentapplication 1001, EMV L2 application 1002, and terminal managementsystem (TMS) 1003 to interface with the embedded operating system 1005of the embedded system (BT OS). In some embodiments, the embeddedoperating system 1005 may be a Linux based system, but is notparticularly limited to a Linux based operating system. The embeddedoperating system 1005 communicates with a plurality of drivers to allowthe embedded system to control a plurality of peripheral devices.Specifically, the embedded system may include a Wi-Fi driver 1006 toallow the operating system 1005 to communicate with a Wi-Fi device 1007,through which the base station 1000 can communicate with the mobiledevices 1100, 1200, 1300.

The authentication between the base station 1000 and one of the mobiledevices 1100, 1200, 1300 is done through the base station WTAapplication 1004 and the WTA application of the respective mobiledevices (or host accessed by the respective mobile devices) 1103, 1203,1303. In other words, one WTA application resides on each of the mobiledevices (host securely accessed by each mobile device through a browser)1100, 1200, 1300, and one WTA application resides on the base station1000. Further, each of the WTA applications 1103, 1203, 1303 of themobile devices 1100, 1200, 1300 authenticate the WTA application 1004 ofthe base station 1000 and the WTA application 1004 of the base station1000 authenticates the WTA applications 1103, 1203, 1303 of therespective mobile devices 1100, 1200, 1300.

Further, there is also additional authentication between the POSapplications 1101, 1201, 1301 of the mobile devices 1100, 1200, 1300 andthe WTA application 1004 of the base station 1000. The POS applications1101, 1201, 1301 may be readily available third party POS applicationsavailable through various mobile device application stores (i.e. iTunesApp store, Android Play store, etc.). However, only POS applications1101, 1201, 1301 of the mobile devices that have been authenticated bythe WTA application of the base station 1000 can use the WTAapplications 1103, 1203, 1303 to communicate with the base station 1000.Thus, even if a user downloads the correct POS application into a mobiledevice, the POS application cannot use the base station 1000 until it isauthenticated because the WTA applications 1004, 1103, 1203, 1303control the data flow between the mobile devices 1100, 1200, 1300 andthe base station 1000.

Additionally, the Terminal Management System (TMS) 1003 includes adownload tool that is used for download authentication for the basestation 1000 when downloading and installing the payment application1001 on the base station 1000. Thus, though the POS applications 1101,1201, 1301 of the mobile devices 1100, 1200, 1300 may be directlydownloadable through online app stores, the TMS 1003 locks down thepayment application 1001 to prevent unauthorized downloading ofapplications into the base station 1000.

Further, the embedded system of the base station 1000 may also include adriver 1008 to allow the base station 1000 to communicate with a cashdrawer 1009 to facilitate making change for cash purchases. A securedstorage driver 1010 may be used to communicate with the secured storagedevice 1011 embedded within the base station 1000. A bar code scannerdriver 1012 may also be provided to allow the base station to interfacewith a bar code scanner or reader 1013. Further, a print driver 1014 mayalso be provided to allow the base station to communicate with a printer1015, either wirelessly or through a wired connection.

Further, a non-volatile memory driver 1016 may be provided to allow thebase station to control a non-volatile memory such as an ElectricallyErasable Programmable Memory (EEPROM) 1017. A unique identifier(VID/PID) and other information can be stored in the non-volatile memory1017 inside base station 1000. The portable devices 1100, 1200, 1300 canuse this data for authentication between the portable devices 1100,1200, 1300 and the base station 1000. Additionally, one or more cardreader drivers 1018, 1019 may be provided to control one or more cardreader modules 1020, 1021. Further, a contactless reader driver 1022 andan external PIN pad driver 1023 may be provided to control an externalcontactless reader 1024 and an external PIN pad 1025. The mobile devices1100, 1200, 1300 and base station 1000 will authenticate the pin pad sothat only an approved PIN pad can be used with the base station 1000 andmobile devices 1100, 1200, 1300. Additionally, in some embodiments, theembedded system of the base station 1000 may also include a customer orshopper display driver 1026 to interface with a display 1027 for ashopper or customer to view the transaction as it is being processed.Additionally, in some embodiments the base station 1000 may include anEthernet driver 1028 to interface with an Ethernet controller.

FIG. 11A provides a block diagram showing a second embodiment of thesoftware level architecture, and interaction between, an embodiment ofthe base station and one or more mobile devices. The second embodimentof the software level architecture shown in FIG. 11A is substantiallysimilar to the embodiment shown in FIG. 10. Thus, similar components arelabeled with the same reference numerals and redundant description isomitted.

In the embodiment shown in FIG. 10, a payment application 1001 wasprovided in the base station 1000 and a payment User InterfaceApplication 1102, 1202, 1302 was provided on each of the mobile devices1100, 1200, 1300. However, embodiments of the present application neednot include a payment application 1001 provided in the base station1000. Instead, as shown in the embodiment of FIG. 11A, a paymentapplication 1107, 1207, 1307 may be separately provided on each of themobile devices 1100, 1200, 1300. By running a payment application 1107,1207, 1307 on the mobile devices 1100, 1200, 1300, the payment userinterface application 1102, 1202, 1302 may be omitted from the mobiledevices 1100, 1200, 1300 and the payment application 1001 may be omittedfrom the base station 1000.

Further, FIG. 11B provides a block diagram showing a third embodiment ofthe software level architecture, and interaction between, an embodimentof the base station and one or more mobile devices. The third embodimentof the software level architecture shown in FIG. 11B is substantiallysimilar to the embodiment shown in FIG. 10. Thus, similar components arelabeled with the same reference numerals and redundant description isomitted.

In the embodiment shown in FIG. 10, a payment application 1001 wasprovided in the base station 1000 and a payment User InterfaceApplication 1102, 1202, 1302 was provided on each of the mobile devices1100, 1200, 1300. However, embodiments of the present application neednot include a payment application 1001 provided in the base station1000. Instead, as shown in the embodiment of FIG. 11B, a thin-clientapplication or browser based application 1108, 1208, 1308 may beseparately provided on each of the mobile devices 1100, 1200, 1300. Byrunning a thin-client application or browser based application 1108,1208, 1308 on the mobile devices 1100, 1200, 1300, the payment userinterface application 1102, 1202, 1302 may be omitted from the mobiledevices 1100, 1200, 1300 and the payment application 1001 may be omittedfrom the base station 1000.

Any of the software components described herein may take a variety offorms. For example, a component may be a stand-alone software package,or it may be a software package incorporated as a “tool” in a largersoftware product. It may be downloadable from a network, for example, awebsite, as a stand-alone product or as an add-in package forinstallation in an existing software application. It may also beavailable as a client-server software application, as a web-enabledsoftware application, and/or as a mobile application.

The above description of the disclosed embodiments is provided to enableany person skilled in the art to make or use the invention. Variousmodifications to these embodiments will be readily apparent to thoseskilled in the art, and the generic principles described herein can beapplied to other embodiments without departing from the spirit or scopeof the invention. Thus, it is to be understood that the description anddrawings presented herein represent a presently preferred embodiment ofthe invention and are therefore representative of the subject matterwhich is broadly contemplated by the present invention. It is furtherunderstood that the scope of the present invention fully encompassesother embodiments that may become obvious to those skilled in the artand that the scope of the present invention is accordingly not limited.

What is claimed is:
 1. A system for processing transactions, comprising: a. at least one mobile device comprising: i. a housing having a processor, and a Wi-Fi communication module disposed therein; and b. a base station comprising; i. a base station housing, wherein the base station housing houses an embedded system comprising:
 1. a processor; and
 2. a Wi-Fi communication module configured to communicate with the Wi-Fi communication module of the at least one mobile device; ii. a support stand configured to support the at least one mobile device, wherein the support stand comprises at least one arm having an adjustable position and configured to move to adjust the size of the support stand based on a size of at least one mobile device; and c. at least one peripheral device connected to base station, wherein the base station further comprises a. a payment module configured to perform payment transactions; and b. a first Wi-Fi transportation application, which causes the processor of the base station to control the payment module and the Wi-Fi communication module of the base station; and c. wherein the at least one mobile device further comprises: i. a payment user interface configured to allow a user to perform payment transactions with the payment module; ii. a Point of Sale (POS) module configured to perform Point of Sale operations; iii. a second Wi-Fi transportation application, which causes the processor of the at least one mobile device to control the POS module and the Wi-Fi communication module of the at least one mobile device; and d. wherein the first Wi-Fi transportation application is configured to cause the processor of the base station to prevent the payment module and the Wi-Fi communication module of the base station from communicating with the POS module, the payment user interface and the Wi-Fi communication module of the at least one mobile device unless the second Wi-Fi transportation application has been authenticated by the first Wi-Fi transportation application; and e. wherein the second Wi-Fi transportation application is configured to cause the processor of the at least one mobile device to prevent the POS module, the payment user interface and the Wi-Fi communication module of the at least one mobile device from communicating with the payment module and Wi-Fi communication module of the base station unless the first Wi-Fi transportation application has been authenticated by the second Wi-Fi transportation application.
 2. The system of claim 1, wherein a plurality of payment modules may be installed in the base station; a. wherein the base station further comprises a terminal management system (TMS) download tool configured to control the processor of the base station to authenticate which of the plurality of payment modules is an authorized payment module; and b. wherein the TMS download tool controls the processor to prevent unauthorized payment applications from communicating with the at least one mobile device.
 3. The system of claim 1, wherein the base station further comprises a secure storage device, and wherein the first Wi-Fi transportation application is further configured to cause the processor of the base station to prevent the at least one mobile device from accessing the secured storage device unless the second Wi-Fi transportation application of the at least one mobile device has been authenticated by the first Wi-Fi transportation application.
 4. The system of claim 3, wherein the POS module is configured to store data relating to performed Point of Sale operations to the secured storage device when the second Wi-Fi transportation application has been authenticated by the first Wi-Fi transportation application.
 5. The system of claim 1, wherein the at least one peripheral device comprises at least one of a pin pad, a keyboard, a user interface, a printer, and a display device.
 6. A system for processing transactions, comprising: a. at least one mobile device comprising: i. a housing having a processor, and a Wi-Fi communication module disposed therein; and b. a base station comprising: i. a base station housing, wherein the base station housing houses an embedded system comprising:
 1. a processor, and
 2. a Wi-Fi communication module configured to communicate with the Wi-Fi communication module of the at least one mobile device: ii. a support stand configured to support the at least one mobile device, wherein the support stand comprises at least one arm having an adjustable position and configured to move to adjust the size of the support stand based on a size of the at least one mobile device; and c. at least one peripheral device connected to the base station, wherein the at least one peripheral device is configured to communicate with the base station and the at least one mobile device via a wireless connection; and a. wherein the at least one peripheral device further comprises a third Wi-Fi transportation application configured to control the at least one peripheral device to prevent the at least one peripheral device from communicating with either the base station or the at least one mobile device unless first and second Wi-Fi transportation applications have been authenticated by the third Wi-Fi transportation application. b. wherein the base station further comprises a first Wi-Fi transportation application configured to control the processor of the base station to prevent the at least one peripheral device from communicating with the base station unless the third Wi-Fi transportation application has been authenticated by the first Wi-Fi transportation application; and c. wherein the at least one mobile device comprises a second Wi-Fi transportation application configured to control the processor of the at least one mobile device to prevent the at least one peripheral device from communicating with the at least one mobile device unless the third Wi-Fi transportation application has been authenticated by the second Wi-Fi transportation application.
 7. The system of claim 6, wherein the at least one peripheral device comprises at least one of a pin pad, a keyboard, a user interface, a printer, and a display device. 